@twastvedt Just out of curiosity: what version of SQL Server are (or were) you using? I thought that this problem only existed in SQL Server 2005, and maybe possibly 2008. If you are using a version newer than 2008, then I am interested in getting more details because I can't reproduce this on newer versions. Thanks!

Huh, strange. We're on SQL Server 2014. Maybe something more was going on than I realized. I'm happy to provide more details if it's useful (not sure what those would be), but also feel free to just close this!

@twastvedt If you are using SQL Server 2014, then the casing of sysname should not be an issue. Do you happen to have the exact error message you were receiving? All I can see in the initial post of this issue is:

an unresolved reference error

I don't see a need to close this just yet if the change you are mentioning did actually fix a problem. I'm just trying to figure out if this is a SQL Server-specific collation issue or something within the tSQLt code itself.

@twastvedt If you are using SQL Server 2014, then the casing of sysname should not be an issue. Do you happen to have the exact error message you were receiving? All I can see in the initial post of this issue is:

an unresolved reference error

I don't see a need to close this just yet if the change you are mentioning did actually fix a problem. I'm just trying to figure out if this is a SQL Server-specific collation issue or something within the tSQLt code itself.

I'm having the same issue.

In my scenaion, tSQLt is being built and deployed using Visual Studio 2019 onto an Azure SQL DB. Happy to provide any further details if requied.

I'm having the same issue.

In my scenario, tSQLt is being built and deployed using Visual Studio 2019 onto an Azure SQL DB. Happy to provide any further details if required.

Hi @T-J-L . Knowing that you are using Visual Studio to deploy certainly helps. Still, I really need the exact and full error message (including error number, etc).

I'm having the same issue.
In my scenario, tSQLt is being built and deployed using Visual Studio 2019 onto an Azure SQL DB. Happy to provide any further details if required.

Hi @T-J-L . Knowing that you are using Visual Studio to deploy certainly helps. Still, I really need the exact and full error message (including error number, etc).

Here you go:

Severity Code Description Project File Line Suppression State
Error SQL71501: Column: [#inputbuffer].[EventType] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [dbo].[SYSNAME] or [tSQLt].[SYSNAME]. Procedures\Private_InputBuffer.sql 5